Received: from alaska.et.byu.edu by darth.byu.edu (NX5.67d/NX3.0M)
id AA00648; Tue, 31 May 94 15:59:01 -0600
Received: from yvax1.byu.edu by alaska.et.byu.edu; Tue, 31 May 1994 08:33:46 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.3-8 #4169)
id <01HCZDXEYUZ49GV6L9@yvax.byu.edu>; Tue, 31 May 1994 08:30:54 MDT
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.3-8 #4169)
id <01HCZDW23NQO019ZZB@yvax.byu.edu>; Tue, 31 May 1994 08:29:41 -0600 (MDT)
Received: from YVAX2.BYU.EDU by alaska.et.byu.edu; Tue,
31 May 1994 08:23:49 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.3-8 #4169)
id <01HCZDNPND68019YDO@yvax.byu.edu>; 31 May 94 08:22:57 -0600 (MDT)
Received: from sxpo.fdn.org by yvax.byu.edu (PMDF V4.3-8 #4169)
id <01HCZDNCO29C019U0V@yvax.byu.edu>; Tue, 31 May 1994 08:22:52 -0600 (MDT)
Received: by sxpo.fdn.org id AA24510
(5.65c8/IDA-1.4.4/FdN-1.0 for byu.edu!misckit); Tue, 31 May 1994 16:22:59 +0100
Received: by improve.fdn.org (NX5.67d/Improve-1.0) id AA00426; Tue,
31 May 94 15:06:40 +0200
Received: by folie. (NX5.67d/Improve-1.0) id AA00219; Tue,
31 May 94 11:20:04 +0100
Received: by NeXT.Mailer (1.100.RR)
Received: by NeXT Mailer (1.100.RR)
Date: Tue, 31 May 1994 11:20:04 +0100
From: Frederic STARK <fred@folie.byu.edu>
Subject: Re: Requesting input for file (p.s.)
To: misckit@byu.edu
Message-Id: <9405311020.AA00219@folie.>
Content-Transfer-Encoding: 7BIT
I agree with the File object approach for storing files, but I believe the FileSearch object is necessary to perform complex search.
I think it (File) could be implemented as a subclass of a more abstract class (something that could be called a GraphNode ?).
So we could make directroy trees of filesystems or netinfo structures or anything else, just by subclasing.
The abstract class should be designed to nicely interact with interfaces object (as NXBrowser).
Here are several design for file manipulation
1) (I did this one once. Worked pretty well.)
File ---> Directory
File:
- Hold file system information (- lstat)
- and a boolean (- (BOOL)isDirectory)
Directory:
- returns YES for - (BOOL)isDirectory
- implements a '- (SortedList *)files'
The problem (for me) with this design is that I don't find it easy to subclass it (For adding display capabilities or anything - like having a TIFFFileClass, an AppWrapperFileClass, a MyDocumentFileClass and so one)
2) If we could allow an extra pointer in the File object, for the SortedList holding the childs, we could merge File and Directory
3) So, we could move the childs list pointer in an upper class to obtain